Course
title: Computer Programming for Business II Spring
2004
Course
number: M&IS 34033 section 001
Course description: Presently using the Java language to emphasize
problem solving, developing systems, structured programming and programming
style conventions.
Location: 108 BSA Meeting
day: W Meeting time: 6:15-8:45 PM
Name: Janet Formichelli, MS
Email: jformich@kent.edu
Office
location: A410 BSA
Office
hours: T 1:30-3:00, 6:00-7:00; W
5:00-6:00; Th 1:30-3:00
Phone: 330-672-1159
Students attending the
course who do not have the proper prerequisite risk being deregistered from the
class.
Enrollment: Students have responsibility to
ensure they are properly enrolled in classes.
You are advised to review your official class schedule during the first
two weeks of the semester to ensure you are properly enrolled in this class and
section. Should you find an error in
your class schedule, you have until Saturday, January 24, 2004 to correct it
with your advising office. If
registration errors are not corrected by this date and you continue to attend
and participate in classes for which you are not officially enrolled, you are
advised now that you will not
receive a grade at the conclusion of the semester for any class in which you
are not properly registered.
Course Goals: To solve
problems and implement these solutions using the Java programming
language.
Summary of key
components of the course:
Introduction to
Applications
· Brief history of Java
· Java class libraries
· Memory concepts
· Inputting and outputting data
· Operators--arithmetic, relational, assignment,
increment, decrement and logical
· Primitive data types
Exception Handling
· try/catch blocks
· common exceptions
Introduction to Applets
· Compiling and executing Applets
· Viewing Applets with appletviewer
· Incorporating Applets in an html file
Graphics
· Color control
· Font control
· Drawing lines, rectangles, ovals and arcs
· Drawing polygons and polylines
Control structures
· if
· if/else
· while
· do/while
· for
· switch
Methods
· Method definitions
· Java API packages
· Methods of class Math
· Methods of class JApplet
· Argument promotion
· Duration of identifiers
· Scope rules
· Method overloading
Arrays
· Arrays--allocating, initializing and using
· References and reference parameters
· Passing arrays to methods
· Sorting and searching arrays
Programming with Objects
and Classes
· Declaring and creating objects
· Differences between primitive types and objects
· Garbage collection
· Accessing an object’s data and methods
· Constructors
· Passing objects to methods
· Visibility modifiers and accessor methods
· Class variables, constants and methods
· Instance variables and class variables
· Scope of class variables
· The keyword this
Inheritance
· Superclasses and subclasses
· The keyword super
· Calling superclass constructors and methods
· Overriding methods
Textbook: Deitel and Deitel, Java: How to Program,
Fourth Edition, Prentice Hall, 2002.
ISBN 0-13-0345151-7
Software
Disk included with book.
Go to WebCT and read “Compiling Java” on the homepage there for complete
information about installing the Java 2 SDK.
WebCT
The WebCT site, http://class.kent.edu or accessible through flashline, will
basically manage the course. The syllabus, assignments, Power Point slides, and other
course information will be found there. A help page for using WebCT is found
at: http://webcthelp.kent.edu/v3/
Course Requirements
6 Java programming assignments: (25 points
hw1, 35 points hw2-6) 200 points
3
course exams: (50 points each) 150 points
final exam: 50
points
Grading Scale
90-100 A 80-89
B 70-79
C 60-69
D 0-59 F
This scale is followed
closely and there is no extra credit.
When there are schedule
changes or other announcements, the instructor will e-mail you using your KSU
e-mail address. Check this frequently. If you commonly use another address, forward
your Kent e-mail to that address. You can do this easily on the Kent Help Desk
site at: http://helpdesk.kent.edu/faq/Email/fmail/
To e-mail the instructor
use: jformich@kent.edu or if you reply to an e-mail from the
instructor with another address, that is ok. Do not e-mail the instructor at
WebCT.
For homework assignments, if
you put the letters hw with a space on each side of the hw in the subject line
of the e-mail, a reply will be generated to you that the instructor has
received your homework. For example:
Subject: Jones hw 5
You will not get the reply
immediately, but you should have it within a day.
Missing class is not an
excuse for failure to understand material or complete assignments. Material covered in class will not be covered
again outside of class. It is up to you to read the material and get notes from
another student if you miss class. Do not expect any special help or privileges
if you do not attend class regularly.
Programming assignments are
to be e-mailed to the instructor by the beginning of the class time on the date
on which they are due. Absence from class is not an excuse for not having the
assignment in. Late assignments will be penalized 10% per day (not per class
session). Assignments will not be
accepted after one week beyond the due date.
Make-up exams are given only
under extraordinary circumstances. Inform the instructor as soon as possible
(ideally before the exam). Some form of written excuse for absence from an exam
is required.
University Policy:
Cheating
means to misrepresent the source, nature, or other conditions of your academic
work (e.g., tests, papers, projects, assignments) so as to get undeserved
credit. The use of the intellectual
property of others without giving them appropriate credit is a serious academic
offense. It is the University's policy
that cheating or plagiarism result in receiving a failing grade for the work or
course. Repeat offenses result in
dismissal from the University.
Course Policy:
Academic
honesty is expected and required. HELPING fellow students is acceptable, and is
actually a very good way to learn the material (particularly with debugging
programs). COPYING is NOT acceptable, and will result in loss of credit for the
assignment, and possibly failure of the course for all students involved.
Follow these guidelines:
All
work on the design and basic coding phase of a program should be your own. That
is, sitting in a group writing a program together is considered to be copying.
If you receive help with
debugging part of an assignment, then you must acknowledge that help in the
documentation of that section (your grade will not be affected).
If
you give help to another student, then it is your responsibility to make sure
that they fully understand the concepts. You may help them to debug the
program, but you may not give them code.
If
copying programs is suspected, both (or all) students involved will receive
zeros for that assignment at the least, and possibly a failure for the course.
DO NOT GIVE OTHERS YOUR CODE.
If
copying programs is suspected, both (or all) students involved will receive
zeros for that assignment at the least, and possibly a failure for the course.
DO NOT GIVE OTHERS YOUR CODE. If they ask you for it, ask to see theirs instead
and help them debug.
In accordance with University
policy, if you have a documented disability and require accommodations to
obtain equal access in this course, please contact the instructor at the
beginning of the semester or when given an assignment for which an
accommodation is required. Students with
disabilities must verify their eligibility through the Office of Student
Disability Services (SDS) in the Michael
Schwartz Service Center
(672-3391).
Week 1 |
Jan. 14 |
Chp. 1, 2 |
|
|
|
|
|
|
|
|
|
Week 2 |
Jan. 21 |
Chp. 3 |
Lab |
|
|
|
|
|
|
|
|
Week 3 |
Jan. 28 |
Chp. 11 |
|
Assignment 1 |
|
|
|
|
|
|
|
Week 4 |
Feb. 4 |
Chp. 11,14 |
|
|
|
|
|
|
|
|
|
Week 5 |
Feb. 11 |
Chp. 4 |
Lab |
|
Exam 1: Chp. 1, 2, 3, 11 |
|
|
|
|
|
|
Week 6 |
Feb. 18 |
Chp. 4, 5 |
|
|
|
|
|
|
|
|
|
Week 7 |
Feb. 25 |
Chp. 5, 6 |
|
|
|
|
|
|
|
|
|
Week 8 |
Mar. 3 |
Chp. 6 |
Lab |
|
|
|
|
|
|
|
|
Week 9 |
Mar. 10 |
Chp. 6 |
|
Assignment 3 |
|
|
|
|
|
|
|
Week 10 |
Mar. 17 |
Chp. 7 |
|
|
Exam 2: Chp. 4, 5, 6 |
Saturday |
Mar. 20 |
|
|
|
Last Day to Withdraw |
|
|
|
|
|
|
|
Mar. 24 |
|
|
|
Spring Break |
|
|
|
|
|
|
Week 11 |
Mar. 31 |
Chp. 7 |
Lab |
|
|
|
|
|
|
|
|
Week 12 |
Apr. 7 |
Chp. 8 |
|
Assignment 4 |
|
|
|
|
|
|
|
Week 13 |
Apr. 14 |
Chp. 8, 9 |
Lab |
|
|
|
|
|
|
|
|
Week 14 |
Apr. 21 |
Chp. 9 |
|
Assignment 5 |
|
|
|
|
|
|
|
Week 15 |
Apr. 28 |
|
Lab |
Assignment 6 |
Exam 3: Chp. 7, 8, 9 |
|
|
|
|
|
Course Evaluation |
Week 16 |
May. 5 |
|
|
|
Final--comprehensive |
|
|
|
|
|
5:45-8:00 PM |
|
|
|
|
|
|
Tentative |
Material Covered |
|
|
|
|
|
|
|
|
|
|
Chapter |
Sections |
||||
1 |
8, 9,13,15 |
||||
2 |
1--8 |
||||
14 |
1--7 |
||||
3 |
1--5 |
||||
11 |
1--7 |
||||
4 |
1--13 |
||||
5 |
1--6,9 |
||||
6 |
1--8, 10, 11,15,16 |
||||
7 |
1--7 |
||||
8 |
1--4, 6--8,13,15 |
||||
9 |
1--9 |